Tiempo para inicio de sesión alto.

El tiempo de espera para iniciar sesión esta entre 15 a 20 y en ocasiones hasta 30 segundos por lo que algunos usuarios les tiran error al iniciar sesión.

 ELMAH

System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out --- End of inner exception stack trace --- at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.Entity.Infrastructure.Interception.InternalDispatcher1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func3 operation, TInterceptionContext interceptionContext, Action3 executing, Action3 executed) at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext) at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) --- End of inner exception stack trace --- at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.ExecuteTResultType at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess) at System.Data.Entity.Core.Objects.ObjectQuery1.<>cDisplayClass7.<getresults>b5() at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func1 operation) at System.Data.Entity.Core.Objects.ObjectQuery1.GetResults(Nullable1 forMergeOption) at System.Data.Entity.Core.Objects.ObjectQuery1.<system.collections.generic.ienumerable<t>.GetEnumerator>b__0() at System.Data.Entity.Internal.LazyEnumerator1.MoveNext() at System.Collections.Generic.List1..ctor(IEnumerable1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source) at Aseinfo.VH4.UI.Web.Controllers.AccountController.Login(String txtUsername, String txtPassword, Boolean chkRememberMe, Nullable`1 isSilverlightInstalled, String returnUrl) in C:vh4VH4UIWebControllersAccountController.cs:line 712

Ante este problema reportado lo que se ha realizado es lo siguiente:

 Se agregó el nombre de dominio al usuario ya que no lo tenía, pero no cambio nada, sigue con el mismo tiempo.

 Se corrió la siguiente función desde el servidor de aplicaciones para probar el usuario de dominio fuera de Evolution, he identificar si también se tardaba el mismo tiempo que en Evolution, pero la respuesta fue rápida.

function Test-ADCredential{ [CmdletBinding()] param( [pscredential]$Credential )

try {
    Add-Type -AssemblyName System.DirectoryServices.AccountManagement
    if(!$Credential) {
        $Credential = Get-Credential -EA Stop
    }
    if($Credential.username.split("\").count -ne 2) {
        throw "Ingrese las credenciales en formato DOMAIN\USERNAME. Valor ingresado: $($Credential.Username)"
    }

    $DomainName = $Credential.username.Split("\")[0]
    $UserName = $Credential.username.Split("\")[1]
    $Password = $Credential.GetNetworkCredential().Password

    $PC = New-Object System.DirectoryServices.AccountManagement.PrincipalContext([System.DirectoryServices.AccountManagement.ContextType]::Domain, $DomainName)
    if($PC.ValidateCredentials($UserName,$Password)) {
        Write-Host "Exitosa la validación de las credenciales del usuario $($Credential.Username)"
        return $True
    } else {
        throw "Fallo la validación de las credenciales para el usuario$($Credential.Username)"
    }
} catch {
    Write-Host "Error ocurrido mientras se validaban las credenciales. $_"
    return $False
}

}

Configuración de Servidor Aplicaciones:

Disco Duro: 200 GB

Memoria RAM: 8.00 GB

Procesador: Intel Xeon CPU E5-2690 0 @ 2.90 GHz (2 Procesadores)

OS: Windows 2016 Standard

IIS: 10.0.14393.0

Configuración de Servidor DB:

Disco Duro OS: 200 GB

Disco Duro E (Backups): 500 GB

Disco Duro F (Datos) : 200 GB

Disco Duro G (Log): 100 GB

Disco Duro H (TempDB): 50 GB

Memoria RAM: 8.00 GB

Procesador: Intel Xeon CPU E5-2650 v2 @ 2.60 Ghz (2 Procesadores)

OS: Windows 2016 Standard 64 bits

Microsoft SQL Server Standard (64-bit) Version: 13.0.4604.0

Version de Evolution

Evolution 1.11.2.3